Vcenter NamespaceManagement Supervisors Workloads
Vcenter NamespaceManagement Supervisors Workloads schema describes configuration that affects the behavior and lifecycle of Kubernetes workloads.
This schema was added in vSphere API 8.0.0.1.
{
"network": {
"network": "string",
"network_type": "string",
"nsx": {
"dvs": "string",
"namespace_subnet_prefix": 0
},
"vsphere": {
"dvpg": "string"
},
"nsx_vpc": {
"nsx_project": "string",
"vpc_connectivity_profile": "string",
"default_private_cidrs": [
{
"address": "string",
"prefix": 0
}
]
},
"services": {
"dns": {
"servers": [
"string"
],
"search_domains": [
"string"
]
},
"ntp": {
"servers": [
"string"
]
}
},
"ip_management": {
"dhcp_enabled": false,
"gateway_address": "string",
"ip_assignments": [
{
"assignee": "string",
"ranges": [
{
"address": "string",
"count": 0
}
]
}
]
}
},
"edge": {
"id": "string",
"load_balancer_address_ranges": [
{
"address": "string",
"count": 0
}
],
"haproxy": {
"servers": [
{
"host": "string",
"port": 0
}
],
"username": "string",
"password": "string",
"certificate_authority_chain": "string"
},
"nsx": {
"edge_cluster_id": "string",
"default_ingress_tls_certificate": "string",
"routing_mode": "string",
"egress_ip_ranges": [
{
"address": "string",
"count": 0
}
],
"t0_gateway": "string",
"load_balancer_size": "string"
},
"nsx_advanced": {
"server": {
"host": "string",
"port": 0
},
"username": "string",
"password": "string",
"certificate_authority_chain": "string",
"cloud_name": "string"
},
"foundation": {
"deployment_target": {
"zones": [
"string"
],
"storage_policy": "string",
"deployment_size": "string",
"availability": "string"
},
"interfaces": [
{
"personas": [
"string"
],
"network": {
"network_type": "string",
"dvpg_network": {
"name": "string",
"network": "string",
"ipam": "string",
"ip_config": {
"ip_ranges": [
{
"address": "string",
"count": 0
}
],
"gateway": "string"
}
}
}
}
],
"network_services": {
"dns": {
"servers": [
"string"
],
"search_domains": [
"string"
]
},
"ntp": {
"servers": [
"string"
]
},
"syslog": {
"endpoint": "string",
"certificate_authority_pem": "string"
}
}
},
"provider": "string"
},
"kube_api_server_options": {
"security": {
"certificate_dns_names": [
"string"
]
}
},
"images": {
"registry": {
"hostname": "string",
"port": 0,
"username": "string",
"password": "string",
"certificate_chain": "string"
},
"repository": "string",
"kubernetes_content_library": "string",
"content_libraries": [
{
"content_library": "string",
"supervisor_services": [
"string"
],
"resource_naming_strategy": "string"
}
]
},
"storage": {
"cloud_native_file_volume": {
"vsan_clusters": [
"string"
]
},
"ephemeral_storage_policy": "string",
"image_storage_policy": "string"
}
}
The workloads Vcenter NamespaceManagement Supervisors Workloads.network describes configuration for the primary workload network.
Workloads will communicate with each other and will reach external networks over this network.
The IP ranges configured on this network are managed primarily within Kubernetes.
This property was added in vSphere API 8.0.0.1.
Vcenter NamespaceManagement Supervisors Workloads.edge configuration determines how network traffic will enter and leave the cluster.
The IP ranges configured on this network are managed by the Supervisor and the load balancer.
This property was added in vSphere API 8.0.0.1.
Vcenter NamespaceManagement Supervisors Workloads.kube_API_server_options declares configuration options for the Kubernetes API Server.
This property was added in vSphere API 8.0.0.1.
If missing or null
, the default configuration will be used.
Vcenter NamespaceManagement Supervisors Workloads.images specifies how images will be stored and pulled into the cluster.
This property was added in vSphere API 8.0.0.1.
If missing or null
, image sync configuration will default to the settings described within the Vcenter NamespaceManagement Supervisors ImageSyncConfig schema.
Vcenter NamespaceManagement Supervisors Workloads.storage specifies which persistent storage is configured and accessible for workloads to consume. You can configure policies for both images and volumes.
This property was added in vSphere API 8.0.0.1.
If missing or null
, configuration will be copied from the control plane when possible. If not, some storage features may be unavailable.